📝 Description

Apply the ScopeType enum pattern from PR #133 to caveat type parameters, allowing both enum references and string literals when defining caveats.

🔄 What Changed?

• Added CaveatType enum to constants.ts with all 26 caveat enforcer function names
• Created ConvertCaveatConfigsToInputs generic type to support flexible caveat type specification (enum or string)
• Updated CaveatConfiguration type to use the flexible type conversion pattern
• Enhanced CaveatBuilder.addCaveat() to normalize and accept both enum and string caveat types
• Updated resolveCaveats() function to handle flexible caveat type normalization
• Exported new types (CaveatType, CoreCaveatConfiguration, ConvertCaveatConfigsToInputs) in public API

🚀 Why?

• Provides consistency with the ScopeType pattern established in PR chore: scope types #133
• Improves API flexibility by allowing users to pass caveat types as either enum references or string literals
• Maintains backward compatibility with existing string-based caveat type usage
• Better type safety with enum references while preserving flexibility of string literals

🧪 How to Test?

• Manual testing steps:
  1. Use CaveatType.AllowedMethods enum reference in caveatBuilder.addCaveat()
  2. Verify it works the same as string literal 'allowedMethods'
  3. Test both patterns in createDelegation caveats array
  4. Verify type completions show both patterns in IDE
• Automated tests added/updated - Existing test suite passes
• All existing tests pass ✓

⚠️ Breaking Changes

• No breaking changes - This is fully backward compatible

📋 Checklist

• Code follows the project's coding standards
• Self-review completed
• Documentation updated (if needed)
• Tests added/updated - All existing tests pass
• All CI checks pass ✓

🔗 Related Issues

Related to #145
Related to PR #133 (ScopeType enum pattern)
Related to PR #137 (enum flexibility pattern)

📚 Additional Notes

This implementation follows the same flexible type pattern established in PR #133 for ScopeType. Both enum references and string literals are supported for maximum flexibility:

// Using enum reference
caveatBuilder.addCaveat(CaveatType.AllowedMethods, { selectors: [...] })

// Using string literal (existing pattern)
caveatBuilder.addCaveat('allowedMethods', { selectors: [...] })

// In createDelegation caveats array
createDelegation({
  from: address,
  to: delegate,
  scope: scopeConfig,
  caveats: [
    { type: CaveatType.ValueLte, maxValue: 1000n },
    { type: 'erc20TransferAmount', tokenAddress: token, maxAmount: 100n }
  ]
})